Technote Number: 1085799
Problem:
This issue was reported to Lotus Software Quality Engineering and has been
addressed in Notes 6.0.1.
Excerpt from the Lotus Notes and Domino fix list
(http://www.lotus.com/ldd/r5fixlist.nsf):
LotusScript
SPR# PALT5GGUL4 - The Editdoc method will now prevent queued messages from
dispatching if a close is pending, preventing a crash.
Workaround:
It is not necessary to place a document into Read mode if the code is going to
execute the Close method directly after calling the Save method. So removing
the EditDocument call is a viable work around for many code scenarios.
If there is additional code between the calls which somehow requires placing
the document into Read mode prior to closing the document, then the work around
is to create an agent with the desired code and then call this agent from the
From Action. Agents may be called from an Action a number of ways:
- Using the Simple Action "Run Agent"
- Using the Formula @Function @Command([ToolsRunMacro])
- Using the LotusScript GetAgent method (of the NotesDatabase class) in
conjunction with the Run method (of the NotesAgent class).
Supporting Information:
The NSD crash stack observed:
############################################################
### FATAL THREAD 1/7 [ NLNOTES:0330:0418]
### FP=0012eecc, PC=611dd250, SP=0012eec0, stksize=12
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x611dd250 nnotesws.CLSUIDocument::RaiseEvent+144 (61b0a598,0,d5,0)
@[ 2] 0x611ddf56 nnotesws._DocScriptRaiseEvent@28+518 (30b6b68,2cec934,d5,0)
@[ 3] 0x612a8dca nnotesws.CBaseDocSelection::CommonCommand+1050
(30b08e8,12f2f8,0,2cec934)
@[ 4] 0x6189ba43 nnotesws.CRODocSelection::CommonCommand+1699
(30b08e8,12f2f8,2cec934,0)
@[ 5] 0x6154bbc1 nnotesws.CROActionSetSelection::ExecuteScriptedObject+129
(30bd8e8,2cec934,0,d5)
@[ 6] 0x61557950 nnotesws.CROActionSelection::Execute+224
(2cec934,901de,30bd8e8,55ed38)
@[ 7] 0x6154c1c0 nnotesws.CROActionSetSelection::CommonCommand+96
(30bd8e8,12f418,c0000000,111)
@[ 8] 0x6155cce7 nnotesws._ActionBarWndProc@16+551 (0,111,80000011,601fc)
[ 9] 0x77e12ca8 USER32.GetSysColor+1092 (6155cac0,901de,111,80000011)
[10] 0x77e14398 USER32.ReleaseDC+321 (55ed38,111,80000011,601fc)
[11] 0x77e153a1 USER32.SendMessageA+59 (901de,111,80000011,601fc)
@[12] 0x6118a4d0 nnotesws._BmpButtonWndProc@16+2560 (30b1ae8,202,0,13000c)
[13] 0x77e12ca8 USER32.GetSysColor+1092 (61189ad0,601fc,202,0)
[14] 0x77e12dc5 USER32.GetSysColor+1377 (12f7c0,0,77e17baf,12f7c0)
[15] 0x77e12f0f USER32.DispatchMessageW+11 (901de,55c548,0,77e15366)
@[16] 0x612c80e5 nnotesws.ModelessWindowDispatch+229 (0,61220010,61180000,1)
@[17] 0x61220228 nnotesws._NEMMainLoop@4+536 (401000,12f0e0,133e0c,0)
@[18] 0x0040156d NLNOTES._WinMain@16+1389 (400000,0,133e0c,1)
@[19] 0x00401dfa NLNOTES._WinMainCRTStartup+308
(12f0e0,77f98191,7ffdf000,12f0f0)
[20] 0x7c4e87f5 KERNEL32.DosDateTimeToFileTime+3172 (401cc6,0,c8,100) More >
|  |
|
|
|
|
|